Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: Release notes for 2.9.0-nRF54H20-1 #19715

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

FrancescoSer
Copy link
Contributor

Added release notes for 2.9.0-nRF54H20
Added migration guide for 2.9.0-nRF54H20
Added other minor release edits for 2.9.0-nRF54H20

@FrancescoSer FrancescoSer added this to the 2.9.0-nRF54H20 milestone Dec 30, 2024
@github-actions github-actions bot added doc-required PR must not be merged without tech writer approval. changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. labels Dec 30, 2024
@NordicBuilder
Copy link
Contributor

NordicBuilder commented Dec 30, 2024

CI Information

To view the history of this post, clich the 'edited' button above
Build number: 32

Inputs:

Sources:

sdk-nrf: PR head: f64b263cb47fb972ff925294d4794cb8aa710039

more details

sdk-nrf:

PR head: f64b263cb47fb972ff925294d4794cb8aa710039
merge base: a14701baea486b7d65771ad3b9826719c60633dd
target head (main): 571676740aacb35db0cc99ee67a5598820ed1c59
Diff

Github labels

Enabled Name Description
ci-disabled Disable the ci execution
ci-all-test Run all of ci, no test spec filtering will be done
ci-force-downstream Force execution of downstream even if twister fails
ci-run-twister Force run twister
ci-run-zephyr-twister Force run zephyr twister
List of changed files detected by CI (33)
doc
│  ├── nrf
│  │  ├── app_dev
│  │  │  ├── device_guides
│  │  │  │  ├── nrf54h
│  │  │  │  │  ├── ug_nrf54h20_gs.rst
│  │  │  │  │  │ ug_nrf54h20_suit_recovery.rst
│  │  ├── conf.py
│  │  ├── dev_model_and_contributions
│  │  │  │ adding_code.rst
│  │  ├── links.txt
│  │  ├── protocols
│  │  │  ├── matter
│  │  │  │  │ index.rst
│  │  ├── releases_and_maturity
│  │  │  ├── abi_compatibility.rst
│  │  │  ├── migration
│  │  │  │  ├── 2.4.99-cs3_to_2.6.99-cs2
│  │  │  │  │  ├── migration_guide_2.4.99-cs3_to_2.6.99-cs2_application.rst
│  │  │  │  │  │ migration_guide_2.4.99-cs3_to_2.6.99-cs2_environment.rst
│  │  │  │  ├── migration_guide_1.x_to_2.x.rst
│  │  │  │  ├── migration_guide_2.4.99-cs3_to_2.6.99-cs2.rst
│  │  │  │  ├── migration_guide_2.5.rst
│  │  │  │  ├── migration_guide_2.6.rst
│  │  │  │  ├── migration_guide_2.7.rst
│  │  │  │  ├── migration_guide_2.8.rst
│  │  │  │  ├── migration_guide_2.9.0-nRF54H20-1.rst
│  │  │  │  ├── migration_guide_2.9.rst
│  │  │  │  ├── migration_guide_3.0.rst
│  │  │  │  ├── migration_guide_nRF54H20_cs_to_2_7.rst
│  │  │  │  ├── migration_guide_nRF54H20_cs_to_2_7_99-cs1.rst
│  │  │  │  ├── migration_guide_nRF54H20_cs_to_2_7_99-cs2.rst
│  │  │  │  ├── migration_hwmv2.rst
│  │  │  │  ├── migration_sysbuild.rst
│  │  │  │  ├── nRF54H20_migration_2.7
│  │  │  │  │  ├── migration_guide_2.4.99-cs3_to_2.7_application.rst
│  │  │  │  │  ├── migration_guide_2.6.99-cs2_to_2.7_application.rst
│  │  │  │  │  ├── migration_guide_2.6.99-cs2_to_2_7_environment.rst
│  │  │  │  │  │ transition_guide_2.4.99-cs3_to_2.7_environment.rst
│  │  │  ├── migration_guides.rst
│  │  │  ├── release_notes.rst
│  │  │  ├── releases
│  │  │  │  ├── release-notes-2.9.0-nRF54H20-1.rst
│  │  │  │  │ release-notes-changelog.rst
│  │  │ shortcuts.txt
│  │ versions.json

Outputs:

Toolchain

Version:
Build docker image:

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

  • ◻️ Toolchain
  • ◻️ Build twister
  • ◻️ Integration tests
Disabled integration tests
    • desktop52_verification
    • doc-internal
    • test_ble_nrf_config
    • test-fw-nrfconnect-apps
    • test-fw-nrfconnect-ble_mesh
    • test-fw-nrfconnect-ble_samples
    • test-fw-nrfconnect-boot
    • test-fw-nrfconnect-chip
    • test-fw-nrfconnect-fem
    • test-fw-nrfconnect-nfc
    • test-fw-nrfconnect-nrf-iot_lwm2m
    • test-fw-nrfconnect-nrf-iot_mosh
    • test-fw-nrfconnect-nrf-iot_positioning
    • test-fw-nrfconnect-nrf-iot_samples
    • test-fw-nrfconnect-nrf-iot_serial_lte_modem
    • test-fw-nrfconnect-nrf-iot_thingy91
    • test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
    • test-fw-nrfconnect-nrf_crypto
    • test-fw-nrfconnect-ps
    • test-fw-nrfconnect-rpc
    • test-fw-nrfconnect-rs
    • test-fw-nrfconnect-tfm
    • test-fw-nrfconnect-thread
    • test-fw-nrfconnect-zigbee
    • test-low-level
    • test-sdk-audio
    • test-sdk-dfu
    • test-sdk-find-my
    • test-sdk-mcuboot
    • test-sdk-pmic-samples
    • test-sdk-sidewalk
    • test-sdk-wifi
    • test-secdom-samples-public

Note: This message is automatically posted and updated by the CI

@github-actions github-actions bot removed the changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. label Dec 30, 2024
@FrancescoSer FrancescoSer force-pushed the relnotes2_9_54h_final branch 2 times, most recently from 2ab556e to 7f63324 Compare January 21, 2025 15:31
Copy link
Contributor

@grochu grochu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add the following note (as described in https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/releases/release-notes-changelog.html#bluetooth_le)
- Fixed an issue where Bluetooth applications built with the nordic-bt-rpc snippet (in the :ref:bt_rpc configuration) did not work on the nRF54H20 devices due to incorrect memory mapping.
PR: #20038

@FrancescoSer FrancescoSer force-pushed the relnotes2_9_54h_final branch 2 times, most recently from a546db2 to f7802a5 Compare January 23, 2025 14:01
@FrancescoSer FrancescoSer force-pushed the relnotes2_9_54h_final branch from f7802a5 to cd4a2dc Compare January 23, 2025 14:17
@FrancescoSer FrancescoSer requested a review from grochu January 23, 2025 14:17
doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_gs.rst Outdated Show resolved Hide resolved

To do that you can simply paste the following code snippet into your configuration files:

.. code-block:: cfg

CONFIG_SUIT_RECOVERY=y
CONFIG_NRF_REGTOOL_GENERATE_UICR=n
CONFIG_NRF_REGTOOL_GENERATE_BICR=n
CONFIG_SOC_NRF54H20_GENERATE_BICR=n
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think the commits that transition away from using nrf-regtool to generate BICR have been merged yet, from what I could tell they will be pulled in with the upmerge. Not sure what the plans are there, but unless that change will be part of this release, I believe the Kconfigs before the edit are still the correct ones to use.

@FrancescoSer FrancescoSer force-pushed the relnotes2_9_54h_final branch 2 times, most recently from 336950b to 9eaeb8b Compare January 28, 2025 15:45
@FrancescoSer FrancescoSer requested a review from peknis January 29, 2025 10:34
@FrancescoSer FrancescoSer force-pushed the relnotes2_9_54h_final branch from 9eaeb8b to 2eeae26 Compare January 29, 2025 10:36
@FrancescoSer FrancescoSer force-pushed the relnotes2_9_54h_final branch from 2eeae26 to b1f5750 Compare January 30, 2025 13:41
Added release notes for 2.9.0-nRF54H20-1.
Added migration guide for 2.9.0-nRF54H20-1.
Added other release edits for 2.9.0-nRF54H20-1.

Signed-off-by: Francesco Domenico Servidio <[email protected]>
@FrancescoSer FrancescoSer force-pushed the relnotes2_9_54h_final branch from ff617ce to f64b263 Compare January 30, 2025 15:14

nrfutil device recover --core Application --serial-number <serial_number>
nrfutil device recover --core Network --serial-number <serial_number>
nrfutil device reset --reset-kind RESET_PIN --serial-number <serial_number>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The nrf-regtool requirements in the NCS build system are incorrectly set for SoC binaries v0.9.0. The STM logging functionality does not work with the minimum required version of the nrf-regtool and that is v8.0.0. Should we mention in the migration guide that the user should migrate to the newest version of nrf-regtool (v8.1.2)?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would also recommend bumping the minimum required version in the build system so users of this NCS release will get a clear build failure if they attempt to build nRF54H projects with an incorrect nrf-regtool version:

https://github.com/nrfconnect/sdk-zephyr/blob/main/modules/hal_nordic/CMakeLists.txt#L18

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the similar migration note for the nrf-regtool from the NCS 2.8 migration guide:

https://github.com/nrfconnect/sdk-nrf/blob/main/doc/nrf/releases_and_maturity/migration/migration_guide_2.8.rst#nrf-regtool

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport v2.9-nRF54H20-branch doc-required PR must not be merged without tech writer approval.
Projects
None yet
Development

Successfully merging this pull request may close these issues.